5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
- Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-4: Files and Fields

Group Trailer Fields


A group trailer field provides an optional way to allow for future additions to the end of a group field. (A group field is a concatenation of fields that can be referenced together by a single field name: the group header field. See the Group Fields section for a discussion of group characteristics.) All fields within a group must have a sequence number that falls between the number you defined for the group header field and that of the field you entered in the Thru Field Name specification.

A group trailer simplifies group field maintenance by providing a placeholder to mark the end of a group. You enter a group trailer field (rather than the final field in a group) in the Thru Field Name specification on the group header field. In the future, any field you add with a sequence number between that of the group header and the group trailer becomes part of the group. It is not necessary to modify the Thru Field Name specification to include the new field.

For example, assume your account number is a group field that is currently composed of a main account, sub account, and division. If you do not use a group trailer, you must identify the division as the final field in the group (with the Thru Field Name specification). If you add a branch component to the end of the account number, you must change the Thru Field Name specification to list the branch, rather than the division, as the final field in the group. If instead, you had used a group trailer as the final field in the group, you could add a branch to the group simply by creating the branch field with a sequence number that is greater than that of the division and smaller than that of the group trailer. You would not be required to alter the Thru Field Name specification.

As with a group header field, the group trailer occupies no physical space in the file. There are no specifications that are unique to a group trailer field.

Application Design Manual                                         "Powered by Appx Software"

217

©2006 By APPX Software, Inc. All Rights Reserved